-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added example utility using OOPS and IODA #553
Conversation
@guillaumevernieres make sure I didn't screw up the merge conflicts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for adding this oops example. This is a handy reference. Changes look good to my inexperienced eyes. I have not installed feature/oops_example
on Hera or Orion and run ctests to ensure everything works a planned. Adding a CI label to this PR will do this for us.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this @CoryMartin-NOAA . I have a minor cosmetic comment that you can decide if you want to address or not. Ready to merge, pending CI results. Code norm to be added in a separate PR.
Automated Global-Workflow GDASApp Testing Results:
|
C++17 on Hera issue fixed by using a function that is 'older'. Not sure why that didn't build, I thought the compiler was new enough on Hera (this is concerning but we will cross that bridge later). Will try to loo into the failing tests some more now. |
@RussTreadon-NOAA I bet this is the culprit: https://github.com/JCSDA-internal/ufo/commit/92f78421da2713bb256f8f758381381060bad6a2
|
Automated Global-Workflow GDASApp Testing Results:
|
Apparently the CI testing does not download the JCSDA test data. @guillaumevernieres @RussTreadon-NOAA should it do that? or should I just manually include/download a single IODA file for this test? I could include one in our testdata tar file. |
Which approach is easier to implement now and maintain moving forward? |
Probably cloning the jcsda test data, but it might be overkill. I'm happy to do that if we think that's the easiest path forward. |
@CoryMartin-NOAA , can you run your test with one of the soca ioda files? soca still uses git-lfs to store binaries. |
I went with @guillaumevernieres 's suggestion, it now uses one of the SOCA test files that have brightnessTemperature as a variable. |
|
Automated Global-Workflow GDASApp Testing Results:
|
The failures are unrelated to this PR it seems, but I defer to @RussTreadon-NOAA and @guillaumevernieres if we want to try to fix them before approving/merging this. |
issue #554 has been opened to report the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been voting for ignoring the atmos ctest for the last few pr's! Looks ready to merge. Thanks again @CoryMartin-NOAA .
This PR adds a very simple utility that will read in a IODA file, and for a specified group/variable, compute the mean and print it out. Nothing too fancy but is a nice C++ OOPS example.